|
|
 |
|
|
|
|
482: '##ModelId=352AB4F0001E
483: Public Sub CancelTrans()
484: End Sub
485:
486: |
|
|
|
|
|
|
|
|
This chapter describes the Database Access Subsystem and its purpose. In particular, it explains ADO, DAO, RDO, and ODBC. You learned about the classes in the Database Access Subsystem, as well as their methods, properties, arguments, and returns. The chapter presents practical guidelines for implementing this subsystem in code and discusses how to incorporate it into the Samsona Bank Teller System example, providing subsystem code listings for the Bank example. |
|
|
|
|
|
|
|
|
Tomorrow, you learn how to bring all the parts of your application together to make your application complete. That is, you learn how to make your subsystems communicate with one another to support the various ways your users use your application. |
|
|
|
|
|
|
|
|
Q What are the three popular data access mechanisms supported in Visual Basic? |
|
|
|
|
|
|
|
|
A ActiveX Data Objects (ADO), Remote Data Objects (RDO), and Data Access Objects (DAO). |
|
|
|
|
|
|
|
|
Q Which data access mechanism has Microsoft embraced as the future standard? |
|
|
|
|
|
|
|
|
Q What is the main goal of this lesson? |
|
|
|
|
|
|
|
|
A To present a common interface for any data access mechanism supported in Visual Basic, especially ADO, RDO, and DAO. |
|
|
|
|
|
|
|
|
Q What is IDatabase in this subsystem? |
|
|
|
|
|
|
|
|
A IDatabase is the common interface shared by objects that participate in the various data access mechanisms Visual Basic developers use. |
|
|
|
|
|
|
|
|
Q True or False: Microsoft doesn't expect ADO to be a superset of RDO. |
|
|
|
|
|
|
|
|
A False. According to Microsoft, ADO will eventually be a superset of RDO. |
|
|
|
|
|